Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@crates/story/examples/fixtures/test.astro`:
- Around line 83-88: The template uses a React-style key prop inside items.map
(the <li key={index}> in the map callback) which is unnecessary in Astro; remove
the key attribute from the <li> elements (or if this JSX-like usage is
intentional for demonstration, add an inline comment near the items.map block
indicating it’s illustrative) so the template emits clean Astro/HTML output;
locate the map invocation (items.map((item, index) => ( ... ))) and either
delete key={index} from the <li> or add a clarifying comment above it.
- Line 6: Remove the unused import GetStaticPaths from the top of the file (the
import statement referencing GetStaticPaths) unless you intend it for
demonstration; if it is meant as an example, replace it with a brief inline
comment clarifying that the import is present only for syntax highlighting/demo,
otherwise delete the import line to eliminate the unused symbol.

In `@crates/story/examples/fixtures/test.kt`:
- Around line 63-67: The function safely currently catches a generic Exception
which triggers the TooGenericExceptionCaught detekt rule; either add
`@Suppress`("TooGenericExceptionCaught") above the safely declaration to silence
the rule, or refactor safely to use Kotlin's runCatching in the safely(block: ()
-> T): Result<T> function (call runCatching { block() } and map success to
Result.Success and failure to Result.Error using the exception.message ?:
"unknown error") so you avoid an explicit catch of Exception.

In `@crates/story/examples/fixtures/test.lua`:
- Line 59: The function declaration HelloWorld:processNames currently defines an
implicit self parameter but doesn't use it, triggering Luacheck W212; either (a)
change the declaration to a dot-style function HelloWorld.processNames(names) if
no instance is needed, or (b) keep the colon and reference self inside the body
or add a Luacheck suppression comment (-- luacheck: ignore 212) directly above
the function to silence the warning; locate the HelloWorld:processNames
definition and apply one of these fixes to remove the unused implicit self
warning.
- Around line 8-112: The Config, LogLevel and describe symbols are unused and
causing Luacheck W211; update HelloWorld.new and/or HelloWorld:generateReport to
reference Config and LogLevel (for example include Config values in self.config
or append LogLevel.DEFAULT to the report) and add a small main/test block that
constructs HelloWorld, calls :generateReport() and calls describe(...) on a
Success/Error and a string to exercise the describe function (use Success/Error
or safely to produce values). Ensure the modifications reference the exact
symbols Config, LogLevel, and describe so they are no longer unused.

In `@crates/story/examples/fixtures/test.svelte`:
- Line 100: The each block using "{`#each` state.items as item, i (item)}" risks
key collisions when duplicate strings exist; change the key to a stable unique
value such as the index or a composite key to guarantee uniqueness (e.g., use
"i" or combine "item" and "i") in the each block that iterates state.items
(references: state.items, item, i, the each block) so Svelte can reliably track
list items.

In `@crates/ui/src/highlighter/highlighter.rs`:
- Around line 41-50: The injection_layers cache is only appended to and can
retain trees for languages whose combined_ranges have been removed; update the
logic in update() to prune injection_layers before parsing new trees: iterate
over the keys in injection_layers and remove any language (key) that is not
present in the current combined_ranges or whose combined_ranges entry is empty,
so InjectionLayer entries are dropped when there are no combined injection
ranges left; keep match_styles() unchanged but rely on the pruned
injection_layers to avoid emitting highlights for non-existent ranges.

In `@crates/ui/src/tree.rs`:
- Around line 396-398: The method signature for focus currently takes &mut self
though it doesn't mutate TreeState; change pub fn focus(&mut self, window: &mut
Window, cx: &mut App) to pub fn focus(&self, window: &mut Window, cx: &mut App)
so callers can use shared refs. Update the impl where focus is defined (the
method named focus that calls self.focus_handle.focus(...)) and ensure
focus_handle.focus accepts &self (no other internal mutability changes
required); then run/adjust any call sites that passed &mut to use & if needed.

In `@docs/docs/components/table.md`:
- Around line 658-669: The events list is missing the ClearSelection event
referenced elsewhere; update the Events section to include the ClearSelection
variant (no payload) alongside the other enum variants (e.g., add
`ClearSelection` to the list) so the API summary and examples match; ensure any
example snippets and references to ClearSelection now point to this documented
event name (ClearSelection) and keep the same formatting as the other entries
like `SelectRow(usize)` and `MoveColumn(usize, usize)`.

---

Outside diff comments:
In `@crates/ui/src/highlighter/languages.rs`:
- Around line 32-133: The test suite is missing coverage for the newly added
Language variants; update the existing test (e.g., test_language_name) to assert
that Language::Kotlin, ::Lua, ::Make, ::Markdown, ::MarkdownInline, ::Php,
::Proto, ::Python, ::Ruby, ::Rust, ::Scala, ::Sql, ::Swift, ::Toml, ::Tsx,
::TypeScript, ::Yaml, and ::Zig map to their expected name() outputs; add each
variant to the test assertions so Language::name() is exercised for all enum
variants and future regressions are caught.

In `@crates/ui/src/table/state.rs`:
- Around line 269-317: Clear any stale right-click state when changing
selection: in set_selected_row and set_selected_col (and in clear_selection),
reset both self.right_clicked_cell = None and self.right_clicked_row = None
whenever you change selection mode/selected items so the old right-click
highlight is removed; update the methods set_selected_row, set_selected_col, and
clear_selection to explicitly clear these fields before emitting
events/notifications.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@crates/story/src/stories/floating_sidebar_story.rs`:
- Around line 43-49: Replace the hardcoded collapsed width px(48.0) with the
existing COLLAPSED_WIDTH constant from the sidebar module: update the local
collapsed_width (and any usages like content_offset) to use COLLAPSED_WIDTH so
the code reads collapsed_width = COLLAPSED_WIDTH (or remove the local var and
substitute COLLAPSED_WIDTH directly), and ensure render_example continues to
reference the same constant for consistency.

In `@crates/ui/src/floating_sidebar/mod.rs`:
- Around line 41-59: FloatingSidebar lacks the Sizable trait required for UI
components; implement impl<E: SidebarItem> Sizable for FloatingSidebar<E> and
add a with_size(self, size: impl Into<Size>) -> Self that forwards the requested
size to the inner Sidebar (or stores it on FloatingSidebar and applies to
Sidebar before layout), ensuring you handle the generic bound E: SidebarItem and
preserve other fields (collapsed, width, min_width, etc.); update any calls that
construct Sidebar inside FloatingSidebar to consume or apply the stored size so
xs/sm/md/lg sizing is respected.

In `@crates/ui/src/highlighter/highlighter.rs`:
- Around line 393-396: Avoid cloning the tree by storing new_tree directly into
self.tree and passing a reference to that stored value to
parse_combined_injections instead of calling new_tree.clone(); specifically,
replace self.tree = Some(new_tree.clone()) with assigning the owned new_tree
into self.tree (self.tree = Some(new_tree)) and then call
parse_combined_injections with a reference obtained from self.tree (e.g.,
self.tree.as_ref().unwrap() or matching on self.tree) so
parse_combined_injections(&...) receives a shared reference to the stored tree.
- Around line 467-486: The injection trees are being reused without applying the
document edit, breaking incremental parsing; in parse_combined_injections (where
you access injection_layers and layer.tree for language_name) stop passing the
stale old_tree into parser.parse_with_options — instead pass None for the old
tree so injections are parsed from scratch (simpler short-term fix), or if you
prefer to preserve incremental parsing, propagate the InputEdit from update()
into parse_combined_injections and call edit() on each old injection tree before
passing it to parser.parse_with_options.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@crates/story/src/main.rs`:
- Around line 164-171: Replace the hardcoded px(48.0) used to compute
collapsed_width in the render logic with the existing COLLAPSED_WIDTH constant
from the sidebar module to ensure consistency; update the expression that sets
collapsed_width (used when self.collapsed is true) to reference
sidebar::COLLAPSED_WIDTH (or the appropriate module path) so that sidebar_width
and content_offset derive from that constant instead of a literal.

In `@crates/ui/src/setting/settings.rs`:
- Around line 349-352: The SidebarShell currently calls
SidebarShell::left(...).resizer_width(px(0.0)) which disables the resize handle;
either remove the .resizer_width(px(0.0)) call to restore a default/visible
resizer, or (if the sidebar is intentionally non-resizable) add a one-line
inline comment next to the SidebarShell::left(...) chain explaining that the
resizer is deliberately disabled for the settings sidebar (reference:
SidebarShell::left and resizer_width(px(0.0)) in settings.rs).
- Around line 73-106: Add a unit test named test_settings_builder that
instantiates the Settings builder, chains the methods use_sidebar_shell(true),
safe_area_top(<Pixels value>), sidebar_shell_inset(<Pixels value>),
sidebar_title("title"), and page_header_action(|_, _| /* closure */), then
assert the backing fields were set: assert_eq!(settings.use_sidebar_shell,
true), assert_eq!(settings.safe_area_top, <expected Pixels>),
assert_eq!(settings.sidebar_shell_inset, <expected Pixels>),
assert_eq!(settings.sidebar_title.as_deref(), Some("title")), and
assert!(settings.page_header_action.is_some()); place this test in a
#[cfg(test)] mod tests in the same file and import any required types (Pixels,
SharedString, Rc) so the test verifies chaining and field assignment for the
methods use_sidebar_shell, safe_area_top, sidebar_shell_inset, sidebar_title,
and page_header_action.

In `@docs/docs/components/settings.md`:
- Line 95: The documentation example uses a raw integer for the inset which may
not compile because sidebar_shell_inset expects something implementing
Into<Pixels>; update the example to pass a Pixels value by calling px(8.0) (or
equivalent constructor) instead of raw 8 so sidebar_shell_inset(...) receives
the correct type; reference the sidebar_shell_inset helper and the px
constructor/Into<Pixels> conversion in the docs.

In `@docs/docs/components/sidebar.md`:
- Line 104: The documentation example uses inset(8) but inset expects an
Into<Pixels>, so update the example to call inset with a Pixels value using the
px helper (e.g., inset(px(8.0)) or inset(px(8))) and mention px/import if
needed; reference the inset method and the Pixels type to locate the example and
ensure it matches the function signature pub fn inset(mut self, inset: impl
Into<Pixels>) -> Self.

---

Duplicate comments:
In `@crates/story/src/stories/floating_sidebar_story.rs`:
- Around line 43-49: The local variable collapsed_width is hardcoded to
px(48.0); replace its usage with the existing COLLAPSED_WIDTH constant from the
sidebar module to ensure consistency. Update the code in
floating_sidebar_story.rs by removing or replacing the collapsed_width variable
and use COLLAPSED_WIDTH in the content_offset calculation (keeping sidebar_width
and inset as-is), and add the appropriate use/import if needed so
COLLAPSED_WIDTH is in scope.

In `@crates/ui/src/floating_sidebar/mod.rs`:
- Around line 41-59: FloatingSidebar lacks the Sizable trait implementation
required by project UI conventions; implement impl<E: SidebarItem + 'static>
Sizable for FloatingSidebar<E> and have its required methods (e.g., current size
getter, set_size/resize, and min/max size accessors as defined by the Sizable
trait in the codebase) read from and update the struct's fields (width,
min_width, max_width, inset, top_inset and resizer_width where applicable), and
ensure any resize callbacks (on_resize_end) are invoked when size changes so the
component behaves consistently with other sizable UI components.

Verify each finding against the current code and only fix it if needed.

Duplicate comments:
In `@crates/ui/src/floating_sidebar/mod.rs`:
- Around line 224-229: FloatingSidebar lacks Sizable support so callers can't
choose xs/sm/md/lg; add an impl and propagate the chosen size. Add a Size field
to FloatingSidebar (default Size::Md), implement impl<E: SidebarItem> Sizable
for FloatingSidebar<E> with getter and setter (e.g., size(&self) -> Size and
set_size(&mut self, s: Size) -> &mut Self), and ensure this stored size is
applied wherever the component composes children or builds styles: forward the
size to inner components (call their .size(self.size) / set_size) and apply to
the StyleRefinement/state used in render (use the size when computing
classes/styles). Update any builders/constructors to set default Size::Md if
missing.

Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In `@crates/ui/src/highlighter/highlighter.rs`:
- Around line 517-579: The loop over self.injection_layers is nondeterministic
because it iterates a HashMap; make iteration deterministic by collecting the
keys (language_name) into a Vec, sort them (e.g., ascending string order), and
then iterate the sorted keys to lookup layer and query from
self.injection_layers and self.injection_queries instead of iterating the map
directly; update the block that currently says "for (language_name, layer) in
&self.injection_layers" to first build and sort the keys and then use those keys
to obtain layer and query so highlight precedence is stable across runs
(references: self.injection_layers, self.injection_queries, the injection layer
loop in highlighter.rs).

---

Duplicate comments:
In `@crates/ui/src/highlighter/highlighter.rs`:
- Around line 476-492: The code is reusing cached injection trees from
self.injection_layers when calling parser.parse_with_options without applying
Tree‑sitter edits, which can lead to stale positions; either stop passing
old_tree for injections (disable incremental reuse) or accept and propagate an
InputEdit into this routine and call layer.tree.edit(&input_edit) on each cached
tree before passing them to parser.parse_with_options; update the logic around
injection_layers, old_tree, and the parse_with_options call to ensure edit() is
invoked on every cached layer.tree (or set old_tree to None) before incremental
parsing.